-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI bumps #110
base: main
Are you sure you want to change the base?
CI bumps #110
Conversation
Bump 2.4.3 -> 2.4.4. Bump 2.5.4 -> 2.5.5. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Version 1.60 supports Go 1.23. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
As of today, Go 1.23 is released and thus Go 1.21.x is no longer supported. Test against the two supported Go branches: 1.22.x and 1.23.x. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
f10e302
to
f8911f6
Compare
Since actions/setup-go@v4 it caches some go directories to speed up building, testing etc. Alas, we link our code against different libseccomp versions, and such caching my screw up builds. To fix this, add libseccomp version information to cache keys. The only way to do so in actions/setup-go is a file, so supply it with libseccomp.pc which contains libseccomp version and is otherwise rarely updated. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
OK, I guess what happens here is actions/setup-go@v5 caches some Go files and then they are restored in an environment with different version of libseccomp installed, resulting in sporadic failures. Let's try to add libseccomp version to cache key. |
It works, and I am seeing from the logs that cache is being reused. That said, it will be an improvement to also cache compiled libseccomp, but that's a task for another PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had one nitpicky comment, but the changes look good to me.
Acked-by: Tom Hromatka <tom.hromatka@oracle.com>
The only change needed is a flag for pip install, as in Ubuntu-24.04 it is patched to error out saying to use apt. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
This is to avoid breaking CI when a new version comes out. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Looks good to me. Thanks, @kolyshkin
|
Please see individual commits for details. This includes bump to Go 1.23.